[libtiff] use builtin as backup so that tiff can be always part of asimage#21975
[libtiff] use builtin as backup so that tiff can be always part of asimage#21975ferdymercury wants to merge 4 commits intoroot-project:masterfrom
Conversation
Test Results 15 files 15 suites 2d 6h 2m 50s ⏱️ Results for commit b97aa10. |
|
This PR is good work. Is anybody needing to generate natively tiff images? The discussion is still open if gif needs to be supported after 6.40... |
|
Thanks!
Not me at the moment, but having an extra ROOT build option assymmetric from png jpeg bmp gif seems weird. Here we remove one ROOT build option at the price of a builtin backup (that seems reasonably easy). This way functionality will be more reproducible in case someone was using asimage_tiff locally but not present in binaries or so.
In my opinion, saving as gif still makes sense when you want to do animated videos via TCanvas::SaveAs(c.gif++NN) that you can easily include in any webpage or in a PPT. Unless there is an alternative way of generating those :) |
|
@bellenot |
It's because the PR rebases the branch before building. (There was a recent change of the name of LZMA merged into master) It can be solved in your local build by changing BUILTIN_LZMA to LZMA in builtins/libtiff/CMakeLists.txt:91 Or alternatively, rebasing the branch into master in your local. Thanks!! |
|
@ferdymercury yes, fixed by git pull, thanks. And see my review. I don't know what |
Thanks, that ON by default, it's a library that enables C++ stream API building (requires C++ compiler). Thanks for the review ! Once it compiles, if you can run the test "simpleImages" from this branch, I am curious to see if Windows got correctly the JPEG library path passed. |
|
|
Thanks! Can you also look at the output log of the configure step of tiff ? I fear that it's not finding the builtin_jpeg path (The CMakeLists is passing JPEG_INCLUDE_DIR to the external project but maybe incorrectly) |
|
Alright: |
|
Here is the full thig: |
|
I've pushed a fix, in case you could retry the configure step now. Thks! |
|
Still no good: |
|
Looking into it |
|
So this works: And keep these line in the The test pass: Looking now for side effects... |
|
And using directly
without modifying the libjpeg builtin CMakeLists would fail? (that would be weird) |
Well, it was failing originally with |
Ahh, maybe it's because this is a typo with double dollars?
should rather be
? |
Good catch! With this, both Let me check both options... |
|
So I confirm that with |
Great, thanks! Yes, I believe that's because JPEG_INCLUDE_DIR is set elsewhere:
so both are interchangeable now. |
No description provided.